Anticipatory responses to commands

ABSTRACT

Responsive to intercepting an outbound command, a command interceptor may, upon determining that the command is associated with a particular category of commands, transmit an anticipatory response to the source of the command, for example, to prematurely indicate that the command has met with success. Accordingly, a given application whose further execution is dependent upon the successful completion of the command may further execute earlier than would be the case if the given application was to await the transmission of the command, the generation of a response indicating success and the receipt of the response indicating success.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/325,543 filed Dec. 1, 2008, which issued as U.S. Pat. No. 8,274,380on Sep. 25, 2012 and which is herein incorporated by reference in itsentirety.

FIELD

The present application relates generally to communication between adevice and a component and, more specifically, to optimizing thecommunication through use of anticipatory responses to commands.

BACKGROUND

A device that reads information from, or writes information to, a smartcard typically does so through the use of a smart card reader. The smartcard reader may be connected, e.g., through a directly wired connectionor a wireless connection, to the device. Specific software, called a“driver”, is generally executed by the device to facilitate readingfrom, and writing to, a memory component of the smart card using thesmart card reader. The driver includes an application programminginterface (API) that allows other programs to issue requests andcommands so that the requests and commands will be understood by thedriver. An API generally comprises a source code interface that acomputer system or program library provides in order to support requestsfor services to be made of the API by a computer program.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the drawings, which show by way ofexample, embodiments, and in which:

FIG. 1 illustrates an environment in which a smart card is illustratedalong with a mobile communication device that communicates wirelesslywith a smart card reader;

FIG. 2 schematically illustrates the mobile communication device of FIG.1;

FIG. 3 schematically illustrates the smart card reader of FIG. 1;

FIG. 4 illustrates a representation of interaction between a smart carddriver module and a command interceptor of the mobile communicationdevice of FIG. 2, the smart card reader of FIG. 3 and the smart card ofFIG. 1;

FIG. 5 illustrates steps in an exemplary method performed by the commandinterceptor of the mobile communication device of FIG. 2;

FIG. 6 illustrates steps in an exemplary method of handling a responseApplication Protocol Data Unit (APDU) at the command interceptor of themobile communication device of FIG. 1;

FIG. 7 illustrates steps of an exemplary method of handling a casewherein the smart card driver module of the mobile communication deviceof FIG. 1 has received incorrect information about the state of thesmart card of FIG. 1; and

FIG. 8 illustrates steps of an exemplary method in which an alterablefrequency of consideration may be incorporated into the method of FIG.5.

DETAILED DESCRIPTION OF THE EMBODIMENTS

When the connection between the device and the smart card reader iswireless, for example, using the Bluetooth™ wireless communicationprotocol, some complications may arise. In a typical transaction, thedevice transmits, over the wireless connection, a request to the smartcard reader and the smart card reader forwards the request to the smartcard. The smart card then responds to the request with a response andthe smart card reader forwards the response, over the wirelessconnection, to the device. Unfortunately, the latency of a round tripcommunication from the device to the smart card and back again limitsthe speed with which the device can make use of the smart card, e.g., toauthenticate a user of the device. To a lesser extent, bandwidthavailable for the connection between device and smart card reader mayalso limit the speed with which the device can make use of the smartcard. The smart card driver is located on the device and has knowledgeof how to talk to the smart card, which has been received by the smartcard reader. There are many cases where, in order to perform anoperation, there is a requirement for several transactions.

Responsive to intercepting an outbound command, such as an APDU, acommand interceptor may transmit an anticipatory response to the sourceof the command, for example, to prematurely indicate that the commandhas met with success. Accordingly, a given application whose furtherexecution is dependent upon the successful completion of the command mayfurther execute earlier than would be the case if the given applicationwas to await the transmission of the command, the generation of aresponse indicating success and the receipt of the response indicatingsuccess.

In accordance with an aspect of the present application there isprovided a method of handling outbound commands. The method includesintercepting a command outbound from a driver module and determiningthat the command will elicit a response selected from among a pluralityof predictable responses. The method further includes selecting ananticipatory response from the plurality of predictable responses andtransmitting the anticipatory response to the driver module. In otheraspects of the present application, a mobile communication device isprovided for carrying out this method and a computer readable medium isprovided for adapting a processor to carry out this method.

In accordance with another aspect of the present application there isprovided a method of handling a response. The method includes receivinga response from a smart card reader coupled to a smart card, determiningthat the response is of a type distinct from a type of responsetransmitted to an associated driver module as an anticipatory responseto the command and storing, in a record, an indication that an incorrectanticipatory response has been transmitted to the associated drivermodule. In other aspects of the present application, a mobilecommunication device is provided for carrying out this method and acomputer readable medium is provided for adapting a processor to carryout this method.

Other aspects and features of the present application will becomeapparent to those of ordinary skill in the art upon review of thefollowing description of specific embodiments of the application inconjunction with the accompanying figures.

FIG. 1 illustrates an exemplary communication system 100 that includes amobile communication device 106 that is enabled to communicatewirelessly with a peripheral device in the form of a smart card reader104. A smart card 102 is illustrated mounted in the smart card reader104. In some embodiments, the smart card 102 may be communicably coupledwith the smart card reader 104 via a wireless link. In still furtherembodiments, the smart card reader 104 may be integrated with the mobilecommunication device 106, in which case, the smart card reader 104 maybe called a component rather than a peripheral.

FIG. 2 illustrates the mobile communication device 106 including ahousing, an input device (e.g., a keyboard 224 having a plurality ofkeys) and an output device (e.g., a display 226), which may be a fullgraphic, or full color, Liquid Crystal Display (LCD). In someembodiments, the display 226 may comprise a touchscreen display. In suchembodiments, the keyboard 224 may comprise a virtual keyboard. Othertypes of output devices may alternatively be utilized. A processingdevice (a microprocessor 228) is shown schematically in FIG. 2 ascoupled between the keyboard 224 and the display 226. The microprocessor228 controls the operation of the display 226, as well as the overalloperation of the mobile communication device 106, in part, responsive toactuation of the keys on the keyboard 224 by a user. Notably, thekeyboard 224 may comprise physical buttons (keys) or, where the display226 is a touchscreen device, the keyboard 224 may be implemented, atleast in part, as “soft keys”. Actuation of a so-called soft keyinvolves either touching the display 226 where the soft key is displayedor actuating a physical button in proximity to an indication, on thedisplay 226, of a temporary action associated with the physical button.

The housing may be elongated vertically, or may take on other sizes andshapes (including clamshell housing structures), Where the keyboard 224includes keys that are associated with at least one alphabetic characterand at least one numeric character, the keyboard 224 may include a modeselection key, or other hardware or software, for switching betweenalphabetic entry and numeric entry.

In addition to the microprocessor 228, other parts of the mobilecommunication device 106 are shown schematically in FIG. 2. These mayinclude a communications subsystem 202, a short-range communicationssubsystem 204, the keyboard 224 and the display 226. The mobilecommunication device 106 may further include other input/output devicessuch as a set of auxiliary I/O devices 206, a serial port 208, a speaker210 and a microphone 212. The mobile communication device 106 mayfurther include memory devices including a flash memory 216 and a RandomAccess Memory (RAM) 218. Furthermore, the mobile communication device106 may include various other device subsystems 220. The mobilecommunication device 106 may have a battery 222 to power the activeelements of the mobile communication device 106. The mobilecommunication device 106 may, for instance, comprise a two-way radiofrequency (RF) communication device having voice and data communicationcapabilities. In addition, the mobile communication device 106 may havethe capability to communicate with other computer systems via theInternet.

Operating system software executed by the microprocessor 228 may bestored in a computer readable medium, such as the flash memory 216, butmay be stored in other types of memory devices, such as a read onlymemory (ROM) or similar storage element. In addition, system software,specific device applications, or parts thereof, may be temporarilyloaded into a volatile store, such as the RAM 218. Communication signalsreceived by the mobile device may also be stored to the RAM 218.

The microprocessor 228, in addition to its operating system functions,enables execution of software applications on the mobile communicationdevice 106. A predetermined set of software applications that controlbasic device operations, such as a voice communications module 230A anda data communications module 230B, may be installed on the mobilecommunication device 106 during manufacture. A smart card (SC) drivermodule 230C may also be installed on the mobile communication device 106during manufacture. Furthermore, a command APDU interceptor 230D mayalso be installed on the mobile communication device 106 to implementaspects of the present disclosure. As well, additional software modules,illustrated as other software modules 230N, which may comprise, forinstance, a personal information manager (PIM) application, may beinstalled during manufacture. The PIM application may be capable oforganizing and managing data items, such as e-mail messages, calendarevents, voice mail messages, appointments, and task items. The PIMapplication may also be capable of sending and receiving data items viaa wireless carrier network. The data items managed by the PIMapplication may be seamlessly integrated, synchronized and updated viathe wireless carrier network with the device user's corresponding dataitems stored or associated with a host computer system.

Communication functions, including data and voice communications, may beperformed through the communication subsystem 202 and through theshort-range communications subsystem 204.

The short-range communications subsystem 204 enables communicationbetween the mobile communication device 106 and other proximate systemsor devices, which need not necessarily be similar devices. For example,the short-range communications subsystem 204 may include a Bluetooth™communication module to provide for communication with the smart cardreader 104 where the smart card reader also implements a Bluetooth™communication module. As another example, the short-range communicationssubsystem 204 may include an infrared device to provide forcommunication with similarly-enabled systems and devices.

FIG. 3 illustrates an example embodiment of the smart card reader 104.The smart card reader 104 includes a controller including at least onesmart card reader microprocessor 310, which is suitably programmed tocontrol the overall operation and functions of the smart card reader104. The smart card reader 104 may also include an output device (e.g.,a display module 312). The smart card reader 104 may further includeperipheral devices or subsystems such as a flash memory 314, a RAM 316,a serial port 318 (e.g., a Universal Serial Bus, or “USB”, port), asmart card reader short-range communications subsystem 320 (e.g., aninfrared transceiver, wireless bus protocol system using a protocol suchas a Bluetooth™), a storage component interface 322 (e.g., for a memorycard or any other data storage device), a pairing-activation inputdevice 324 (e.g., a push button) and a biometric information inputdevice 325 (e.g., a fingerprint sensor). In some embodiments, the RAM316 includes a portion allocated to a data cache.

The smart card reader microprocessor 310 operates under stored programcontrol with code or firmware being stored in the flash memory 314 (orother type of non-volatile memory device or devices). As depicted inFIG. 3, the stored programs (e.g., firmware) include an operating systemprogram or code module 326 and other programs or software applicationmodules indicated generally by reference 328. The operating systemmodule 326 of the smart card reader 104 further includes a smart cardreader driver component 332.

The smart card reader driver component 332 is responsible forcoordinating communications between the smart card reader 104 and thesmart card 102 and/or the smart card driver module 230C of the mobilecommunication device 106. Based on results of various communicationswith the smart card reader 104, the smart card driver module 230Cmaintains a record of the state of the smart card 102. The operatingsystem module code 326, code for specific device application modules328, code for the smart card reader driver component 332, or codecomponents thereof, may be temporarily loaded into a volatile storagemedium such as the RAM 316. Received communication signals and otherdata may also be stored in the RAM 316. Additionally, the storagecomponent interface 322 receives the smart card 102, which may provideadditional storage space for the smart card reader 104.

In one embodiment, the smart card 102 has a controller 338 responsiblefor coordinating communications between the smart card 102 and the smartcard reader driver component 332 of the smart card reader 104.

The stored program control (i.e., software application modules 328) forthe smart card reader microprocessor 310 may include a predetermined setof applications, code components or software modules that control basicdevice operations, for example, management and security related controlof the data of the smart card reader 104, and may be installed on thesmart card reader 104 as a component of the software application modules328 during the manufacturing process. Further applications may also beloaded (i.e., downloaded) onto the smart card reader 104 through theoperation of the serial port 318, the smart card reader short-rangecommunications subsystem 320 or from the smart card 102. The downloadedcode modules or components may then be installed by the user (orautomatically) in the RAM 316 or non-volatile program memory (e.g., theflash memory 314).

While the smart card reader driver component 332 is shown to be anintegrated portion of the operating system 326 for security purposes(e.g., individuals are not permitted to tamper with the smart cardreader driver component 332), the smart card reader driver component 332may be installed as one of the software applications 328, and in suchembodiments, suitable security related precautions may be taken toensure that the smart card reader driver component 332 cannot bemodified or tampered with by unauthorized users.

The serial port 318 may be a USB-type interface port for interfacing orsynchronizing with another device, such as a personal computer or themobile communication device 106. The serial port 318 is used to setpreferences through an external device or software application orexchange data with a device, such as the mobile communication device106. Such data may be stored on the smart card 120 that is plugged intothe storage component interface 322 of the smart card reader 104. Theserial port 318 is also used to extend the capabilities of the smartcard reader 104 by providing for downloads, to the smart card reader104, of information or software, including user interface information.

The short-range communications subsystem 320 provides an interface forcommunication between the mobile communication device 106 or personalcomputer and the smart card reader 104. In one embodiment, theshort-range communications subsystem 320 employs an infraredcommunication link or channel. In another embodiment, the short-rangecommunications subsystem 320 operates according to a wireless RF busprotocol, such as Bluetooth™. However, the short-range communicationssubsystem 320 may operate according to any suitable local wired orwireless communication protocol, so long as the short-rangecommunications subsystem 204 (FIG. 2) of the mobile communication device106 operates using the same protocol, thereby facilitating wirelesscommunication between the mobile communication device 106 and the smartcard reader 104. Any communications mechanism and/or protocol may beimplemented for the short-range communications subsystems 204, 320, solong as the mobile communication device 106 can communicate with thesmart card reader 104 when the mobile communication device 106 is nomore than a predetermined distance away from the smart card reader 104.

Traditionally, a smart card driver module is supplied by themanufacturer of the smart card 102. The operating system of the mobilecommunication device 106 includes an API. Aspects of the API define asmart card framework. The smart card driver module 230C registers withthe operating system of the mobile communication device 106 so thatcalls to smart card framework aspects of the API can be appropriatelyhandled by the smart card driver module 230C.

Communication between the smart card reader 104 and the smart card 102may be standardized to use Application Protocol Data Units (APDUs),where a standard structure for an APDU is defined by ISO 7816. ISO 7816is an international standard related to electronic identification cards,especially smart cards, managed jointly by the InternationalOrganization for Standardization (ISO) and the InternationalElectrotechnical Commission (IEC). It may be considered that there arevarious categories of APDUs including command APDUs and response APDUs.A command APDU is sent by the smart card reader 104 to the smart card102. A command APDU contains a header and may contain data. A responseAPDU is sent by the smart card 102 to the smart card reader 104. Aresponse APDU contains a status word and may contain data.

When the given application executed on the microprocessor 228 of themobile communication device 106 requires input from the smart card 102,the given application sends an initial request to the smart cardframework, which request is redirected, by the smart card framework, tothe smart card driver module 230C, which is also executed by themicroprocessor 228. Responsive to receiving the request, the smart carddriver module 230C issues a request command APDU to the smart card 102,via the smart card reader 104. Upon receiving the request command APDUfrom the smart card driver module 230C, the smart card reader 104forwards the request command APDU to the smart card 102. Note that, ingeneral, a request command APDU may be transmitted to the smart card 102in bits and pieces, e.g., in a series of packets. Such piecewisetransmission is provided for in protocols known as T=0 and T=1 as partof ISO 7816. The smart card 102 receives the request command APDU andresponds by sending a response APDU to the smart card reader 104. Thesmart card reader 104, upon receiving the response APDU, forwards theresponse APDU to the smart card driver module 230C. Responsive toreceiving the response APDU, the smart card driver module 230C generatesa response and transmits the response to the given application.

It can be documented that wireless communication (sending and receivingeach packet) between the smart card reader 104 and the mobilecommunication device 106 is associated with a greater amount of latencythan wired communication of the same packets. As a result, operations onthe mobile communication device 106, when the operations involve use ofa wireless channel to the smart card reader 104, can, due to thislatency, take significantly longer than when the operations involve useof a wired channel to the smart card reader 104. It is, therefore,desirable to reduce, to a practical extent, the latency associated withthe exchange of packets between the mobile communication device 106 andthe smart card reader 104.

It has been discussed that the smart card reader driver module 230C onthe mobile communication device 106 generates command APDUs. While thereare many possible command APDUs, the command APDUs may be divided intocommand APDUs that have a predictable set of possible response APDUs andall other command APDUs (i.e., those command APDUs whose set of possibleresponse APDUs do not form a predictable set).

For example, a command APDU such as the “SELECT FILE” command APDU maybe considered to be in the category of command APDUs that have apredictable set of possible response APDUs. The “SELECT FILE” commandAPDU usually elicits a response APDU indicating success or a responseAPDU indicating failure. In contrast, a command APDU requestingencryption of some data will elicit a response carrying a payload thatdepends on, inter alia, the data that is to be encrypted, the key usedfor encryption and the method of encryption.

For a more exhaustive study of indications that may be found in aresponse APDU that the smart card 102 transmits in response to the“SELECT FILE” command APDU, see part 4 of ISO 7816 and, in particular,Section 6: Basic Interindustry Commands. The status condition indicatedin a response APDU (responsive to the SELECT FILE command APDU) may beascertained by reviewing status bytes SW1 and SW2. For example, aresponse APDU that indicates successful implementation of a receivedcommand APDU may have the following values in the status bytes:SW1=0x90; and SW2=0x00.

A response APDU (responsive to the SELECT FILE command APDU) thatindicates a warning regarding implementation of a received command APDUmay have the following values in the status bytes: SW1=0x62 and SW2=0x83(selected file invalidated) or SW2=0x84 (not formatted properly).

A response APDU (responsive to the SELECT FILE command APDU) thatindicates an error (i.e., a failure) in implementing a received commandAPDU may have the following values in the status bytes: SW1=0x6A; andSW2=0x81 (Function not supported); or SW2=0x82 (File not found); orSW2=0x86 (Incorrect parameters P1-P2); or SW2=0x87 (Lc inconsistent withP1-P2).

By bypassing a wait for a number of packets to be exchanged over awireless channel between the mobile communication device 106 and thesmart card reader 104, the latency of operations that use the wirelesschannel can be reduced.

In overview, by intercepting command APDUs outbound from the smart cardreader driver 230C and categorizing the command APDUs, the command APDUinterceptor 230D may identify a specific type of command APDU thatelicits a predictable response APDU. By generating the predictableresponse APDU and transmitting the predictable response APDU to thesmart card reader driver 230C, command APDU interceptor 230D may reducethe latency of operations that use the wireless channel.

In view of FIG. 4, the command APDU interceptor 230D may intercept (step502) a command APDU 404 generated by the smart card driver module 230C,before the smart card driver module 230C is able to transmit the commandAPDU 404 over the wireless connection to the smart card reader 104.Notably, the smart card driver module 230C may have generated thecommand APDU 404 responsive to receiving a command 402 from a givenapplication.

Intercepting the command APDU 404 may involve delaying transmission ofthe command APDU 404 to the smart card reader 104 while providing thesmart card driver module 230C with an indication that the command APDU404 has been transmitted.

Alternatively, intercepting the command APDU 404 may involve merely“listening in” as the smart card driver module 230C transmits thecommand APDU 404 To the smart card reader 104, such that the commandAPDU interceptor 230D obtains a copy of the command APDU 404.

The command APDU interceptor 230D may then categorize (step 504) theintercepted command APDU 404, that is, the command APDU interceptor 230Dmay associate the intercepted command APDU 404 with a category. Oneexample category with which the intercepted command APDU 404 may beassociated is a category of command APDUs that elicit, from thedestination smart card, a response APDU selected from among apredictable set of possible response APDUs. One example category withwhich the intercepted command APDU 404 may be associated is a categoryof command APDUs that elicit, from the destination smart card, aresponse APDU that does not come from a predictable set of possibleresponse APDUs.

In the case wherein the command APDU interceptor 230D determines (step506) that the intercepted command APDU 404 is categorized as a commandAPDU whose response APDU does not come from a predictable set ofpossible response APDUs, the command APDU interceptor 230D may transmit(step 508), without further processing, the command APDU 404 over thewireless connection to the smart card reader 104.

In the case wherein the command APDU interceptor 230D determines (step506) that the command APDU 404 has been categorized (step 504) as acommand APDU that elicits a response APDU selected from a predictableset of possible response APDUs, the command APDU interceptor 230D mayselect (step 510) an anticipatory response APDU 406 from among thepredictable set of possible response APDUs. For example, where thepredictable set of possible response APDUs includes a response APDU thatindicates success, the command APDU interceptor 230D may select, as theanticipatory response APDU 406, the response APDU that indicatessuccess, The command APDU interceptor 230D may then transmit (step 512),to the smart card driver module 230C, the anticipatory response APDU406. Additionally, the command APDU interceptor 230D may transmit (step508) the command APDU 404 to the smart card reader 104 over the wirelessconnection.

The transmission (step 508), by the command APDU interceptor 230D, ofthe command APDU 404 over the wireless connection to the smart cardreader 104 may only be necessary in the event that the interception(step 502) of the command APDU 404 has involved delaying thetransmission of the command APDU 404 over the wireless connection to thesmart card reader 104.

Thus, the smart card driver module 230C may be given an indication (bythe anticipatory response APDU 406) that the command carried in thepayload of the command APDU 404 has been carried out successfully by thesmart card 102, thereby allowing the smart card 102 to transmit aresponse APDU indicating success. Responsive to receiving theanticipatory response APDU 406, the smart card driver module 230Cgenerates a response 408 and transmits the response 408 to the givenapplication.

Responsive to receiving the command APDU 404, the smart card reader 104passes the command APDU 404 to the smart card 102, at which the commandAPDU 404 is processed. Following the processing of the command APDU 404,the smart card 102 passes a response APDU 410 to the smart card reader104. The smart card reader 104 then transmits the response APDU 410,over the wireless connection, to the mobile communication device 106.

FIG. 6 illustrates steps in an exemplary method of handling the responseAPDU 410 at the command APDU interceptor 230D of the mobilecommunication device 106. Initially, the command APDU interceptor 230Dreceives (step 602) the response APDU 410. In the case wherein, uponinspecting (step 604) the response APDU 410, the command APDUinterceptor 230D determines (step 606) that the response APDU 410includes an indication of success, the command APDU interceptor 230Dneed not carry out any further steps relative to this exchange of APDUs,since the command APDU interceptor 230D has already transmitted (step512) the anticipatory response APDU 406 indicating success to the smartcard driver module 230C. Conveniently, before sending the response 408,the smart card driver module 230C did not wait for the command APDU 404to be sent, over the wireless connection, to the smart card reader 104;the processing of the command APDU 404 by the smart card 102, leading tothe generation, by the smart card 102, of the response APDU 410; and thereceipt of the response APDU 410, over the wireless connection.

In the case wherein, upon inspecting (step 604) the response APDU 410,the command APDU interceptor 230D determines (step 606) that theresponse APDU 410 includes an indication of failure, the command APDUinterceptor 230D stores (step 610) a record that indicates that thesmart card driver module 230C has received an incorrect anticipatoryresponse. Based on storage of the record that indicates that the smartcard driver module 230C has received an incorrect anticipatory response,the command APDU interceptor 230D may be considered to store anindication that that the smart card driver module 230C is likely to bemaintaining incorrect information about the state of the smart card 102.Optionally, ahead of storing (step 610) the record, the command APDUinterceptor 230D may increase (step 608) a counter of incorrectresponses.

FIG. 7 illustrates steps of an exemplary method of handling the casewherein the smart card driver module 230C has received an incorrectanticipatory response. Upon receiving (step 702) a subsequent commandAPDU 414 from the smart card driver module 230C, the command APDUinterceptor 230D consults (step 704) the record that indicates whetherthe smart card driver module 230C has received an incorrect anticipatoryresponse. The subsequent command APDU 414 may have been generated by thesmart card driver module 230C responsive to having received a subsequentcommand 412 from the given application.

In a first scenario, upon determining (step 706) that the smart carddriver module 230C is likely to be maintaining an incorrect state of thesmart card 102, the command APDU interceptor 230D generates (step 708) a“smart-card-removed” response APDU 416A that indicates that the smartcard 102 has been removed from the smart card reader 104. In the casewherein the smart card 102 and the smart card reader 104 communicatewirelessly rather than via a physical connection, a “smart-card-removed”response may be used to indicate that the smart card 102 and the smartcard reader 104 have become uncoupled. Subsequently, the command APDUinterceptor 230D transmits (step 710), to the smart card driver module230C, the “smart-card-removed” response APDU 416A.

Responsive to receiving the “smart-card-removed” response APDU 416A, thesmart card driver module 230C resets the record of the state of thesmart card 102. Once the smart card driver module 230C has reset therecord of the state of the smart card 102, the smart card driver module230C may issue a further command APDU (not shown), where the furthercommand APDU is very similar to the subsequent command APDU 414, but isbased on a different assumption of the state of the smart card 102.

In a second scenario, upon determining (step 706) that the smart carddriver module 230C is likely to be maintaining a correct state of thesmart card 102, the command APDU interceptor 230D proceeds to executethe method of FIG. 5. That is, the command APDU interceptor 230Dcategorizes (step 504) the subsequent command APDU 414 as either acommand APDU with a predictable set of possible response APDUs or acommand APDU whose set of possible response APDUs do not form apredictable set of possible response APDUs. In the case wherein thecommand APDU interceptor 230D determines (step 506) that the subsequentcommand APDU 414 has been categorized (in step 504) as a command APDUwhose set of possible response APDUs do not form a predictable set ofpossible response APDUs, the command APDU interceptor 230D may transmit(step 508) the subsequent command APDU 414 over the wireless connectionto the smart card reader 104.

However, in the case wherein the command APDU interceptor 230Ddetermines (step 506) that the subsequent command APDU 414 has beencategorized (in step 504) as a command APDU with a predictable set ofpossible response APDUs, the command APDU interceptor 230D may select(step 510) an anticipatory response APDU 416B from among the predictableset of possible response APDUs. The command APDU interceptor 230D maythen transmit (step 512), to the smart card driver module 230C, theanticipatory response APDU 416B. Additionally, the command APDUinterceptor 230D may transmit (step 508) the subsequent command APDU 414to the smart card reader 104 over the wireless connection.

The smart card driver module 230C may be given an indication (by theanticipatory response APDU 416B) that the subsequent command APDU 414has met with success. Responsive to receiving the anticipatory responseAPDU 416B, the smart card driver module 230C generates a response 418and transmits the response 418 to the given application.

Accordingly, it is contemplated that the command APDU interceptor 230Dmay keep track of transmitted incorrect anticipatory responses (see step608, FIG. 6). Based on a determined rate of transmission of incorrectanticipatory responses, the command APDU interceptor 230D may adjust afrequency with which intercepted command APDUs are considered aspredictable candidates for anticipatory responses. For example, thecommand APDU interceptor 230D may consider every second interceptedcommand APDU, every third intercepted command APDU, . . . , every tenthintercepted command APDU, etc. A method in which an alterable frequencyof consideration may be incorporated into the method of FIG. 5 isillustrated in FIG. 8.

The method illustrated in FIG. 8 begins when the command APDUinterceptor 230D intercepts (step 802) a command APDU. Responsive tointercepting a command APDU, the command APDU interceptor 230Dincrements (step 804) an APDU counter. The command APDU interceptor 230Dthen determines (step 806) whether the APDU counter has reached apredetermined value, “X”. Upon determining that the APDU counter hasreached value X, the command APDU interceptor 230D resets (step 808) theAPDU counter to zero. Subsequent to resetting the APDU counter, thecommand APDU interceptor 230D proceeds to execute the method of FIG. 5,That is, the command APDU interceptor 230D categorizes (step 504) thecommand APDU intercepted in step 802 as either a command APDU with apredictable set of possible response APDUs or a command APDU whose setof possible response APDUs do not form a predictable set of possibleresponse APDUs.

Upon determining (step 806) that the APDU counter has not yet reachedvalue X, the command APDU interceptor 230D transmits (step 810) thecommand APDU intercepted in step 802 to the smart card reader 104. Thatis, the command APDU interceptor 230D does not interfere with the normalprogression of the APDU exchange. Instead of examining every interceptedcommand APDU for eligibility for generating an anticipatory APDU, asperhaps suggested by the method of FIG. 5, every X intercepted commandAPDU is examined more closely for the opportunity of sending ananticipatory response APDU. Accordingly, the apparent latency of theAPDU exchange is only reduced for every X intercepted command APDU.

The value of X may be initialized to a first value. However, asoperation of the command APDU interceptor 230D is carried out, an aspectof the command APDU interceptor 230D may monitor the counter ofincorrect anticipatory response APDUs (counted in step 608). Based on adetermined rate of transmission of incorrect anticipatory responseAPDUs, the command APDU interceptor 230D may adjust a frequency withwhich intercepted command APDUs are considered as candidates foranticipatory responses. The rate of transmission of incorrectanticipatory response APDUs may be determined from a count of totalintercepted command APDUs and the count held at a given time in thecounter of incorrect anticipatory response APDUs (counted in step 608).

If a frequency exceeds a predetermined maximum, the command APDUinterceptor 230D may adjust the value of X so that relatively fewerintercepted command APDUs are considered as candidates for theanticipator response APDU.

Advantageously, according to various embodiments of the presentapplication, while the volume of traffic between the mobilecommunication device 106 and the smart card reader 104 remainsunchanged, the delay between the given application sending an initialcommand 402 and receiving the response 408 (based on the anticipatoryresponse APDU 406) may frequently be reduced.

The above-described embodiments of the present application are intendedto be examples only. Alterations, modifications and variations may beeffected to the particular embodiments by those skilled in the artwithout departing from the scope of the application, which is defined bythe claims appended hereto.

What is claimed is:
 1. A method of handling a response, said methodcomprising: receiving a response from a component, said responseresponsive to a command previously transmitted to said component;determining that said response is indicative of failure whereas aresponse transmitted to an associated module as an anticipatory responseto said command was indicative of success; and storing, in a record, anindication that an incorrect anticipatory response has been transmittedto said associated module.
 2. The method of claim 1, further comprising,responsive to said determining, incrementing a counter of incorrectanticipatory responses provided to said associated module.
 3. The methodof claim 1, further comprising receiving said response over a wirelesscommunication channel.
 4. The method of claim 3, wherein said wirelesscommunication channel comprises a Bluetooth communication channel. 5.The method of claim 1, wherein said command is a command ApplicationProtocol Data Unit (APDU) and said response is a response APDU.
 6. Amethod of handling a response, said method comprising: receiving aresponse from a peripheral device, said response responsive to a commandpreviously transmitted to said peripheral device; determining that saidresponse is indicative of failure whereas a response transmitted to anassociated module as an anticipatory response to said command wasindicative of success; and storing, in a record, an indication that anincorrect anticipatory response has been transmitted to said associatedmodule.
 7. The method of claim 6, further comprising, responsive to saiddetermining, incrementing a counter of incorrect anticipatory responsesprovided to said associated module.
 8. The method of claim 6, furthercomprising receiving said response over a wireless communicationchannel.
 9. The method of claim 8, wherein said wireless communicationchannel comprises a Bluetooth communication channel.
 10. The method ofclaim 6, wherein said command is a command Application Protocol DataUnit (APDU) and said response is a response APDU.
 11. A mobilecommunication device comprising: a memory; and a processor operative to:receive a response from a component, said response responsive to acommand previously transmitted to said component; determine that saidresponse is indicative of failure whereas a response transmitted to anassociated module as an anticipatory response to said command wasindicative of success; and store, in a record in said memory, anindication that an incorrect anticipatory response has been transmittedto said associated module.
 12. The mobile communication device of claim11, further comprising a counter for counting incorrect responsesprovided to said associated module, wherein said processor is operativeto increment said counter responsive to determining that said responseis indicative of failure whereas a response transmitted to saidassociated module as an anticipatory response to said command wasindicative of success.
 13. The mobile communication device of claim 11,further comprising a short-range communication subsystem adapted toreceive said response over a wireless communication channel.
 14. Themobile communication device of claim 13, wherein said wirelesscommunication channel comprises a Bluetooth communication channel. 15.The mobile communication device of claim 11, wherein said command is acommand Application Protocol Data Unit (APDU) and said response is aresponse APDU.
 16. A mobile communication device comprising: a memory;and a processor operative to: receive a response from a peripheraldevice, said response responsive to a command previously transmitted tosaid peripheral device; determine that said response is indicative offailure whereas a response transmitted to an associated module as ananticipatory response to said command was indicative of success; andstore, in a record in said memory, an indication that an incorrectanticipatory response has been transmitted to said associated module.17. The mobile communication device of claim 16 further comprising acounter for counting incorrect responses provided to said associatedmodule, wherein said processor is operative to increment said counterresponsive to determining that said response is indicative of failurewhereas a response transmitted to said associated module as ananticipatory response to said command was indicative of success.
 18. Themobile communication device of claim 16, further comprising ashort-range communication subsystem adapted to receive said responseover a wireless communication channel.
 19. The mobile communicationdevice of claim 18, wherein said wireless communication channelcomprises a Bluetooth communication channel.
 20. The mobilecommunication device of claim 16, wherein said command is a commandApplication Protocol Data Unit (APDU) and said response is a responseAPDU.
 21. A non-transitory computer-readable medium containingcomputer-executable instructions that, when performed by a processor ina mobile communication device, result in: receiving a response from acomponent, said response responsive to a command previously transmittedto said component; determining that said response is indicative offailure whereas a response transmitted to an associated module as ananticipatory response to said command was indicative of success; andstoring, in a record, an indication that an incorrect anticipatoryresponse has been transmitted to said associated module.
 22. Thenon-transitory computer-readable medium of claim 21, wherein saidinstructions, when performed by the processor, further result inincrementing a counter of incorrect anticipatory responses provided tosaid associated module.
 23. The non-transitory computer-readable mediumof claim 21, wherein said instructions, when performed by the processor,further result in receiving said response over a wireless communicationchannel.
 24. The non-transitory computer-readable medium of claim 23wherein said wireless communication channel comprises a Bluetoothcommunication channel.
 25. The non-transitory computer-readable mediumof claim 21 wherein said command is a command Application Protocol DataUnit (APDU) and said response is a response APDU.
 26. A non-transitorycomputer-readable medium containing computer-executable instructionsthat, when performed by a processor in a mobile communication device,result in: receiving a response from a peripheral device, said responseresponsive to a command previously transmitted to said peripheraldevice; determining that said response is indicative of failure whereasa response transmitted to an associated module as an anticipatoryresponse to said command was indicative of success; and storing, in arecord, an indication that an incorrect anticipatory response has beentransmitted to said associated module.
 27. The non-transitorycomputer-readable medium of claim 26, wherein said instructions, whenperformed by the processor, further result in incrementing a counter ofincorrect anticipatory responses provided to said associated module. 28.The non-transitory computer-readable medium of claim 26, wherein saidinstructions, when performed by the processor, further result inreceiving said response over a wireless communication channel.
 29. Thenon-transitory computer-readable medium of claim 28, wherein saidwireless communication channel comprises a Bluetooth communicationchannel.
 30. The non-transitory computer-readable medium of claim 26wherein said command is a command Application Protocol Data Unit (APDU)and said response is a response APDU.